Skip to main content

Environment Deployment

The Environment Deployment interface allows users to manage and promote their projects through different deployment stages, such as Development, Testing, and Production. This structured deployment flow ensures seamless transitions from development to live environments, simplifying updates and ensuring system stability.

Key Sections of the Environment Deployment Page​

Development Stage​

This is where new features, bug fixes, and other changes are initially developed.

  • In the Development stage, the current version is shown (e.g., 1.0.0).
  • Users can Deploy Changes to this stage as needed.
  • If issues arise, you can easily Roll Back to a previous stable version.
Example

In the Development stage, changes can be deployed frequently, and once stable, they can be promoted to the Testing environment.

Testing Stage​

After changes in the Development stage have stabilized, they can be promoted to the Testing stage for further validation.

  • The Promote to Testing button enables the movement of the latest stable version to the Testing stage.
  • This stage provides an environment for conducting final tests before deploying to production.
Example

In the image, the Testing stage is using version 1.0.0, which is ready to be promoted to production after testing.

Production Stage​

The Production stage is the live environment accessible by end users.

  • Once the project passes all tests in the Testing stage, it can be Promoted to Production.
  • The production environment should only receive thoroughly tested and validated changes to avoid user-facing issues.
Example

In the image, the Production stage has version 1.0.0, which is currently live for users.

Promoting to the Next Stage​

When your project is ready to progress:

  • Click Promote to Testing or Promote to Production depending on the current stage.
  • This ensures a smooth and controlled transition, minimizing risks associated with live updates.
Example

After deploying and testing changes in the Development stage, you can promote the version to Testing, and once validated, promote it to Production.

Versioning​

Versioning helps track changes across all stages.

  • Each stage displays the current version with options to view Logs or detailed descriptions of changes made in that version.
  • Versioning is critical for rolling back to a previous state if necessary.
Example

Version 1.0.0 is consistent across all stages in the image (Development, Testing, Production), helping you track deployment progression.

Benefits of the Environment Deployment Page​

  • Safe Deployment: Each environment (Development, Testing, Production) provides a safety net by allowing staged deployment.
  • Version Control: Each stage is versioned, offering the ability to track and roll back to earlier versions when needed.
  • Flexible Promotions: Control when to promote changes to testing or production, ensuring that only stable features reach users.
  • Comprehensive Logs and History: Logs help monitor and audit changes across versions, ensuring accountability.
tip

Always thoroughly test your changes in the Testing environment before promoting them to Production. This minimizes risks and ensures a smooth transition for end-users.